Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.13.0 #169

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 16, 2023

Bumps github.com/onsi/ginkgo/v2 from 2.1.4 to 2.13.0.

Release notes

Sourced from github.com/onsi/ginkgo/v2's releases.

v2.13.0

2.13.0

Features

Add PreviewSpect() to enable programmatic preview access to the suite report (fixes #1225)

v2.12.1

2.12.1

Fixes

  • Print logr prefix if it exists (#1275) [90d4846]

Maintenance

  • Bump actions/checkout from 3 to 4 (#1271) [555f543]
  • Bump golang.org/x/sys from 0.11.0 to 0.12.0 (#1270) [d867b7d]

v2.12.0

2.12.0

Features

  • feat: allow MustPassRepeatedly decorator to be set at suite level (#1266) [05de518]

Fixes

  • fix-errors-in-readme (#1244) [27c2f5d]

Maintenance

Various chores/dependency bumps.

v2.11.0

2.11.0

In prior versions of Ginkgo specs the CLI filter flags (e.g. --focus, --label-filter) would override any programmatic focus. This behavior has proved surprising and confusing in at least the following ways:

  • users cannot combine programmatic filters and CLI filters to more efficiently select subsets of tests
  • CLI filters can override programmatic focus on CI systems resulting in an exit code of 0 despite the presence of (incorrectly!) committed focused specs.

Going forward Ginkgo will AND all programmatic and CLI filters. Moreover, the presence of any programmatic focused tests will always result in a non-zero exit code.

This change is technically a change in Ginkgo's external contract and may require some users to make changes to successfully adopt. Specifically: it's possible some users were intentionally using CLI filters to override programmatic focus. If this is you please open an issue so we can explore solutions to the underlying problem you are trying to solve.

Fixes

  • Programmatic focus is no longer overwrriten by CLI filters [d6bba86]

Maintenance

  • Bump github.com/onsi/gomega from 1.27.7 to 1.27.8 (#1218) [4a70a38]
  • Bump golang.org/x/sys from 0.8.0 to 0.9.0 (#1219) [97eda4d]

... (truncated)

Changelog

Sourced from github.com/onsi/ginkgo/v2's changelog.

2.13.0

Features

Add PreviewSpect() to enable programmatic preview access to the suite report (fixes #1225)

2.12.1

Fixes

  • Print logr prefix if it exists (#1275) [90d4846]

Maintenance

  • Bump actions/checkout from 3 to 4 (#1271) [555f543]
  • Bump golang.org/x/sys from 0.11.0 to 0.12.0 (#1270) [d867b7d]

2.12.0

Features

  • feat: allow MustPassRepeatedly decorator to be set at suite level (#1266) [05de518]

Fixes

  • fix-errors-in-readme (#1244) [27c2f5d]

Maintenance

Various chores/dependency bumps.

2.11.0

In prior versions of Ginkgo specs the CLI filter flags (e.g. --focus, --label-filter) would override any programmatic focus. This behavior has proved surprising and confusing in at least the following ways:

  • users cannot combine programmatic filters and CLI filters to more efficiently select subsets of tests
  • CLI filters can override programmatic focus on CI systems resulting in an exit code of 0 despite the presence of (incorrectly!) committed focused specs.

Going forward Ginkgo will AND all programmatic and CLI filters. Moreover, the presence of any programmatic focused tests will always result in a non-zero exit code.

This change is technically a change in Ginkgo's external contract and may require some users to make changes to successfully adopt. Specifically: it's possible some users were intentionally using CLI filters to override programmatic focus. If this is you please open an issue so we can explore solutions to the underlying problem you are trying to solve.

Fixes

  • Programmatic focus is no longer overwrriten by CLI filters [d6bba86]

Maintenance

  • Bump github.com/onsi/gomega from 1.27.7 to 1.27.8 (#1218) [4a70a38]
  • Bump golang.org/x/sys from 0.8.0 to 0.9.0 (#1219) [97eda4d]

2.10.0

Features

... (truncated)

Commits
  • 52065f1 v2.13.0
  • 2c4ed32 remove errant fmt.Println from integration suite
  • 6c84b35 Preview now works alongside run and in parallel
  • e1d0b38 Add PreviewSpecs() to enable programmatic preview access to the suite report
  • 1d2fb67 v2.12.1
  • 90d4846 Print logr prefix if it exists (#1275)
  • 555f543 Bump actions/checkout from 3 to 4 (#1271)
  • d867b7d Bump golang.org/x/sys from 0.11.0 to 0.12.0 (#1270)
  • 2d6991a v2.12.0
  • 05de518 feat: allow MustPassRepeatedly decorator to be set at suite level (#1266)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.1.4 to 2.13.0.
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](onsi/ginkgo@v2.1.4...v2.13.0)

---
updated-dependencies:
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from weizhoublue as a code owner October 16, 2023 09:50
@dependabot dependabot bot added pr/dependabot/gomod This pull is for gomod from dependabot pr/release/none-required not show up in a new release labels Oct 16, 2023
@codecov
Copy link

codecov bot commented Oct 16, 2023

Codecov Report

Merging #169 (bbeee85) into main (0de07d9) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##            main    #169   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          1       1           
  Lines        120     120           
=====================================
  Misses       120     120           
Flag Coverage Δ
unittests 0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 13, 2023

Superseded by #177.

@dependabot dependabot bot closed this Nov 13, 2023
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/onsi/ginkgo/v2-2.13.0 branch November 13, 2023 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/dependabot/gomod This pull is for gomod from dependabot pr/release/none-required not show up in a new release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants